Description

This PR updates the CLA assistant GitHub Action with a couple changes:

• Update the location of the CLA and signatures list to point to a repo under the SpecterOps org
• Change the the CLA check to only occur for members outside of the SpecterOps org

The CLA check is now intended to be run only for contributors outside of the SpecterOps organization. This is implemented by a API lookup of all org members prior to running the CLA Assistant and adding them the to the whitelist parameter of the Action.

Motivation and Context

Resolves BED-5922

Why is this change required? What problem does it solve?

The CLA repo is moving under the SpecterOps organization instead of the legacy BloodHoundAD org.

How Has This Been Tested?

• Tested the action functions as expected on a separate test repo

Types of changes

• Chore (a change that does not modify the application functionality)

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README BloodHound#672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

Summary by CodeRabbit

• Chores
  • Updated the CLA signing workflow to trigger on both created and edited issue comments with specific phrases.
  • Updated references and URLs from "BloodHoundAD" to "SpecterOps" in the CLA process.